Home »
Software Engineering
Software Reuse: Definition and Advantages
In this tutorial, we will learn about the concept of software reuse in software engineering, advantages of software reuse, what can be reused, and basic issues in any reuse program.
By Monika Sharma Last updated : April 07, 2023
Advantages of software reuse
- Software products are costly.
-
Software project managers are worried about the expensive software development and are desperately find for ways to cut development cost are,
- A possible way to reduce development costs is to use parts again from previously developed software.
- In addition to decrease development cost and time, use again also leads to the higher quality of the developed products.
What can be reused?
It is great to know about the kinds of artifacts associated with software development that can be used again. Almost all artifacts associated with software development, including project plan and test plan, can be used again. However, the important items that can be effectively used again are,
- Requirements specification
- Design
- Code
- Test cases
- Knowledge
Basic issues in any reuse program
The following are some of the basic issues that must be for starting any reuse program,
- Component creation
- Component indexing and storing
- Component search
- Component understanding
- Component adaptation
- Repository maintenance
Let's discuss each in details.
1) Component creation
The reusable components have to be first identified. The selection of the correct kind of components having the potential for reuse is best.
2) Component indexing and storing
Indexing requires classification of the again usable components so that they can be easily found when looking for a component for reuse. The components need to be stored in a Relational Database Management System (RDBMS) or an Object-Oriented Database System (ODBMS) for efficient access when the number of components becomes large.
3) Component searching
The programmers need to search for correct components matching their needs in a database of components. To be able to search components efficiently, the programmers require a perfect method to tells the components that they are looking for.
4) Component understanding
The programmers need a prefect and sufficiently complete understanding of what the component does to be able to decide whether they can reuse the component or not. To understand, the components should be well documented and should do something simple in the code.
5) Component adaptation
Before they can be reused, the components may need adaptation, since a selected component may not exactly be mixed the problem at hand. However, tinkering with the code is also not the best solution because this is very likely to be a source of faults.
6) Repository maintenance
It once is created requires repeated maintenance. New components, as and when made have to be entered inside the repository. The faulty components have to be followed.
Further, when new applications mixed, the older applications become obsolete. In this case, the obsolete components might have to be deleted from the repository.
Domain Analysis
The aim is to find the reusable pieces for a problem domain.